home *** CD-ROM | disk | FTP | other *** search
- Original author : Heiner Schneegold
- Translation by : Thorsten Behrens
- Referenced T version: VT2.88
-
- If there are problems that might depend on the translation, send a short
- e-mail to "thorsten.behrens@dorunth.hb.north.de" describing your problem.
- I can't answer questions relating to any technical details of VT. However,
- I can try to clarify your questions from the original german documents.
-
- I won't take any warranty if, based on this translation, damage is done to
- your system. The only valid documents are the original german documents that
- came along with VTx.yz.
-
- Remember to regurlarly backup your system!
-
- === Translation starts here ===================================================
-
- Last Change: 05.03.96
-
- Short operation instructions on VT
- ==================================
-
- Starting up
- ===========
-
- Please start VT with a double click on its icon or using the CLI/Shell.
-
- Hint for users with low memory:
- -------------------------------
- If VT won't start up and if you've got only 1 MB of memory, the reason
- may be that your memory became too fragmented. Either reset your Amiga
- or use KReset (in folder VT.Utilities).
-
- If VT still won't start up, then open a CLI/Shell and format a disk
- using the command
-
- "format DRIVE df0: NAME VTTest2" <return>
-
- After the disk is formatted type in
-
- "install df0:" <return>
-
- Now, copy only the file VT2.xy to this disk ("xy" denotes the version
- you are about to install). Reboot your computer, open a CLI/Shell and
- start VT using the command
-
- "VT2.xy" <return>
-
- Now, VT should run. If you own 2 MB of memory your problems should be
- much less.
-
- Having run VT from disk, please remove the disk not before the screen
- of VT has opened. This is because starting with VT2.50 VT uses tool
- types. These could have been changed using the workbench menu item
- "Icon/Information...". This only makes sense when using WB 2.0 or
- higher together with ECS or AGA. Please note upper and lower case:
-
- (SCREEN=NTSC)
- (SCREEN=PAL)
- (SCREEN=PROD)
- (SCREEN=DblPAL)
- (SCREEN=DblNTSC_640x400)
- (SCREEN=EURO72_640x400)
- (SCREEN=Picasso_640x480)
- (SCREEN=Picasso_800x600)
- (SCREEN=Picasso_1024x768)
- (SCREEN=Picasso_1280x1024)
- (SCREEN=Piccolo_640x480)
- (SCREEN=Piccolo_800x600)
- (SCREEN=Piccolo_1024x768)
- (SCREEN=Piccolo_1280x1024i)
- (SCREEN=S72_800x600i)
- (SCREEN=CyberVis_640x480)
- (SCREEN=CyberVis_800x600)
- (SCREEN=PubWB)
-
- Tool types written in brackets are not active.
- If the last tool type is activated, starting with KS2.04 VT tries to
- use the mode and screen size from your workbench.
-
- If you're starting VT from CLI/Shell, you can use the follwing para-
- meters:
-
- VTx.yz -i = NTSC Interlace 640x400
- VTx.yz -p = PAL 640x256
-
- The following parameters need KS2.04 or higher and ECS or AGA:
- VTx.yz -Pro = Productivity 640x480
- VTx.yz -Dbl = DblPAL
- VTx.yz -DbN = DblNTSC 640x400
- VTx.yz -E72 = EURO72 640x400
- VTx.yz -Pi4 = Picasso 640x480
- VTx.yz -Pi6 = Picasso 800x600
- VTx.yz -Pi7 = Picasso 1024x768
- VTx.yz -P10 = Picasso 1280x1024
- VTx.yz -Pc4 = Piccolo 640x480
- VTx.yz -Pc6 = Piccolo 800x600
- VTx.yz -Pc7 = Piccolo 1024x768
- VTx.yz -Pc1 = Piccolo 1280x1024i
- VTx.yz -S72 = SUPER72 800x600i
- VTx.yz -C48 = CyberVision 640x480
- VTx.yz -C60 = CyberVision 800x600
- VTx.yz -PWB = try to use workbench screen size and mode
-
- If you are an owner of an A4000 or A1200 using a 1084S monitor, you can
- remove all types except PAL and NTSC from your devs/monitors folder. The
- other modes are of no use for you. Another way is to disable "???Mode
- übernehmen???" in Prefs/IControl. This swicth is of no use with your
- hardware. Think about buying a new monitor.
-
-
- System-Check
- ============
-
- After being started, VT checks some conditions:
-
- * The Operating System being used (KickRom V1.2, V1.3,V2.0 oder V3.0)
-
- * Running on PAL screen
-
- * A new window is opened (this has always to occur)
-
- * VT checks some operating system vectors and displays their values
-
- * If there is a difference to the normal values, VT acts accordingly
-
- * The search for known viruses starts
-
- * If this search reveals a known virus, VT displays its name, resets
- the changed vectors, displays them and overwrites the virus with
- null bytes. A reset is not necessary.
-
- * With some viruses it is necessary to delete the virus before displaying
- the vectors (eg with "Extreme") and to fill up its code hunk with null
- bytes. If this happens, a requester pops up showing the name of this
- virus.
-
- * If VT does not know the program responsible for changing the vectors,
- a requester pops up displaying "unbekanntes Programm im Speicher"
- (in english: "unknown program in memory"). If you choose "KReset" on
- this requester, VT resets all changed vectors and reboots. The reason
- for this is, that simply reseting the vectors may not be sufficient to
- get rid off the program. Rather the complete task has to be removed.
- This switch allows rebooting your Amiga without having to switch it
- off. The other switch on the named requester ("Weiter") (in english:
- "Continue") just skips reseting the vectors and removing this program
- and continue with VT.
-
-
- VT's main window
- ================
-
- Haing done the first checks, VT opens its main window. Before going on, two
- important notes:
-
- * If you're planing to write to disk: Always set the original vectors,
- even if you have to restart some important program after VT has done
- its task (resident structures are lost if vectors are reset). To ac-
- complish this: Click on the field labeled "Tools" or press "T" on your
- keyboard. Afterwards click on the button labeled "Setze OVek" (in
- english: "Set original vectors").
-
- * Always work on a copy of the program/disk to be checked.
- Nobody's perfect!
-
- If a requester pops up while working with VT, you may answer to this
- requester according to the Commodore Style Guide:
-
- left gadget : press left Amiga key together with "V" key
- right gadget: press left Amiga key together with "B" key
-
- Some letters of some of the fields are underlined. This means: This field
- may be activated by pressing the underlined key. If this field invokes
- more than a single action (eg "Blockkette", "BlockITest" etc) VT interprets
- this as invoking this field on device "df0:". On other fields a window
- opens which lets you make your choice.
-
- VT is terminated by either clicking on "Ende" (in english: "Stop") or by
- pressing "E".
-
- The switch labeled "Listen" (in english: "list") allows to get a quick
- overview on your system (eg Is SnoopDos running? Find some virus task ...)
- You'll get a menu you may choose from (eg "Resident"). These lists are
- read anew every time you click on "Listen".
-
- ATTENTION: Be careful, if clicking on "Resident" reveals some addresses
- outside ROM (ie greater than $F80000 or $FC0000)!
-
- Note to "IntVecExec": KS 2.04 or higher mounts the Audio-Device ("Aud0"
- to "Aud3") not before these are addressed by a
- task. The original value of an IntVec will be
- shown, although the administration of these is
- done by lists. Viruses are not always programed
- in that way and set these to their own values
- (very popular ist nr. 5 = VertB). (Example: DASA)
-
- You can leave these lists by either pressing <ESC> or using the right
- mouse button.
-
- If you want a printout of these lists, just click on "Druck" (in english:
- "Print").
-
- CheckDisk (CheckD)
- ==================
-
- Some users of VT suggested to do more than a single test on a disk using
- only a single mouse click. This is what the field "CheckD" is for. There-
- for first click on "CPrefs" and enter your preferences. Whenever you now
- click on "CheckD" all your tests will be done one after another. To end
- this test press the <ESC> key until "CheckD-Ende" will be displayed.
-
- Speciality: During the BootBlock test a text just like in the normal
- test is displayed below "Ende". If this is a non-standard
- boot block, the loop stops with a requester. You can now
- take a look at the boot block and afterwards go on with your
- tests by clicking on "Weiter" (in english: "Continue"). If
- this is a known virus boot block another requester pops up
- which lets you install an original Commodore boot block from
- expansions.lib. VT tries to use the correct DOS variant of
- the boot block (ie "DOS0" to "DOS5"). However, if you are not
- sure, whether it may be a special game loading boot block
- (after installing an original boot block, this game will
- surely not start up!!!), cancel this requester (<ESC>). Make
- a copy of this disk, install an original boot block and try
- whether the game starts up. Thanks!
-
- When running a series of tests using "CheckD" file viruses may be removed.
- "CheckD" works on both DD and HD disks, however it is able to use it on
- MSDOS disks. MSDOS disks have to be checked using the appropriate gadgets
- (eg. "PC0:")
-
-
- CPrefs
- ======
-
- Please activate the tests of your choice here (checkmarked) and afterwards
- click on "Ende".
-
-
- Testing a disk
- ==============
-
- There are four different tests: BootBlock test, File test, BlockI test and
- BlockKette test. If ou want a disk to be checked for viruses, you should
- consider doing all tests. To do so, first click on "RootBlock" or press
- "R". You can now choose the device to be tested (eg "DF0:" for the internal
- disk drive).
-
- For File test, BlockI test or BlockKette test there are two switches
- labeled "DF0:" and "Devs:". If you do not want to check df0: click on
- "Devs:" and choose the drive to be tested. To stop a test press the <ESC>
- key or use the right button of your mouse.
-
- A more detailed description of VT may be found in the file named "VTx.xxd"
- which can be found in the folder "VT.Dokumente" (x.xx refers to your version
- of VT).
-
- Heiner Schneegold
-
- This file was originally written by the editors of the Amiga magazine.
-
- Author of VT: Heiner Schneegold
- Am Steinert 8
- 97246 Eibelstadt
- Deutschland
- Tel: 09303/99104
- (19.00 - 20.00 only)
-